Integrated wi-fi location

ABSTRACT

An apparatus includes an integrated circuit that includes a microprocessor and a microcontroller unit circuit (MCU) coupled to the microprocessor. The MCU includes a central processing unit (CPU) core and a network processor that implements a wireless interface. The MCU is configured to execute a location application that facilitates a determination of a physical location of the apparatus. The MCU may also be configured to support one or more management functions. The microprocessor sends data to the MCU for wireless transmission by the MCU&#39;s wireless interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 17/371,433, filed Jul. 9, 2021, which is a division of U.S. patent application Ser. No. 16/425,839, filed May 29, 2019, now U.S. Pat. No. 11,096,012, which applications are hereby incorporated herein by reference.

BACKGROUND

Many portable electronic devices used, for example, in enterprise settings incorporate Wi-Fi for data communication. Examples of such portable devices include logic analyzers used in corporate labs and patient bedside monitors used in hospitals. These products typically execute an embedded high-level operating system such as Linux and are plugged into the building electrical power system. When the equipment is powered, data may be captured, displayed locally and transmitted via an internal Wi-Fi interface to a remote device (e.g., a centralized server or database). When the equipment is not powered, the Wi-Fi connection is lost. When not needed, portable equipment often is unplugged from a power outlet (e.g., wall outlet, power strip).

The enterprise may desire to track the location of the equipment, even when the equipment is powered off. Accordingly, some enterprises use self-contained battery-powered radio location tags for equipment tracking purposes. Various radio frequency (RF) protocols can be used for tracking purposes including Bluetooth, sub-1 GHz and Wi-Fi. When Wi-Fi is used for location, a Wi-Fi tag is adhered to the exterior of equipment to be tracked and can exchange wireless signals with a Wi-Fi access point for location determination purposes.

SUMMARY

In one example, an apparatus includes an integrated circuit that includes a microprocessor and a microcontroller unit circuit (MCU) coupled to the microprocessor. The MCU includes a central processing unit (CPU) core and a network processor that implements a wireless interface. The MCU is configured to execute a location application that facilitates a determination of a physical location of the apparatus. The microprocessor sends data to the MCU for wireless transmission by the MCU's wireless interface.

BRIEF DESCRIPTION OF THE DRAWINGS

For a detailed description of various examples, reference will now be made to the accompanying drawings in which:

FIG. 1 illustrates a hardware diagram of a system in accordance with the described examples.

FIG. 2 illustrates a software architecture implemented on the system of FIG. 1 .

DETAILED DESCRIPTION

The equipment described above typically includes an embedded host system and a Wi-Fi interface. The embedded host system includes a processor, memory, and a Wi-Fi transceiver. The Wi-Fi tag is a self-contained battery powered device that is physically attached to the equipment after purchase. The Wi-Fi tag includes its own Wi-Fi transceiver coupled to a network processor and a microprocessor. The Wi-Fi tag is battery-powered and the embedded host system is line-powered. When line-powered, the embedded host system executes an application (e.g., logic analyzer application, patient bedside monitor application, etc.). The embedded host system uses its own Wi-Fi transceiver to send and receive data wirelessly when executing the embedded application. Often, such transmissions are secured through the use of protocols such as Transport Layer Security (TLS) that rely on security certificates. In one example, a security certificate is generated by a Certificate Authority (CA) and used to digitally sign and verify a communication to/from the embedded host system. Such security certificates often have a defined lifetime, at the end of which the certificate is no longer valid and must be re-generated by the CA and stored in non-volatile memory in the embedded system.

As explained above, the Wi-Fi tag has its own Wi-Fi transceiver, network processor, and microcontroller that executes a location application usable to assist the network in which the equipment operates to determine an approximate physical location of the equipment (e.g., room-level accuracy). As the Wi-Fi tag is battery-operated, the network can determine the physical location of the equipment whether or not the equipment's embedded system is line-powered and operational. However, because the Wi-Fi tag typically is an after-market, external addition to the equipment that includes a second Wi-Fi interface, it adds considerable cost in terms of added equipment and technician installation time. The equipment is line powered, and when line power is not available the equipment cannot connect to the network and cannot be managed remotely. For example, a new security certificate cannot be wirelessly transmitted to and stored in the embedded system. Instead, the equipment would need to be located via the battery-powered Wi-Fi tag, physically brought to a maintenance area, and turned on via line power so that its security certificate can be replaced.

The innovative system described below includes a power-efficient Wi-Fi transceiver that is shared by both the embedded system's line-powered processor, as well as the location system's microcontroller unit (MCU). Thus, two separate Wi-Fi transceivers are not necessary for location and embedded application purposes. Further, the power architecture for the system described below is different than for the conventional system described above. In the conventional system described above, the Wi-Fi tag receives its power only from its battery, while the embedded system receives line power (when available). The system described below, however, includes a power circuit that provides line power (when available) to both the embedded system and the location system. When line power is not available, the power circuit operationally couples a battery to the power efficient location system, but not the embedded system. Accordingly, power is continually provided to the location system and location determinations can be made whether or not the equipment receives line power and the embedded system is powered on.

The location system also includes a flash memory device, which thus is operable from line power or battery power. The flash memory device of the location system can be used to receive and store security certificates used by the location system or by the embedded system. Because the location system operates from battery power when line power is unavailable and the location system includes both the Wi-Fi transceiver as well as the flash memory device, new security certificates can be wirelessly received by the location system even when line power is unavailable, thereby avoiding the manual effort of locating the equipment, physically moving it to a maintenance area, and turning it on to be able provide it with a new security certificate.

FIG. 1 shows an example of an apparatus 100 that includes an embedded system 101, a location system 118, a power circuit 130, and a battery 140. Additional components can be included as desired. The embedded system 101 includes a microprocessor unit (MPU) 102 (also termed a “processor”), a display 103, flash memory 104, and random-access memory (RAM) 106. The location system 118 includes a microcontroller unit (MCU) 120 (also termed a “processor”), flash memory 122, and a sensor 119 (e.g., a motion sensor, a temperature sensor, etc.). The flash memories 104 and 122 comprise re-programmable, non-transitory storage devices and can be used to store, for example, executable code, security certificates, and other information.

The MPU 102 of the embedded system 101 executes an application 107 stored in flash memory 104. The application 107 may be executed directly from flash memory 104, or may be copied to RAM 106 for execution therefrom. When executed, the application 107 causes the MPU 102 to implement one or more functions for apparatus 100. For example, the application 107 can cause the MPU 102 to acquire data, display data on display 103, and transmit data wirelessly to a device remote from the apparatus 100. The application 107 may cause the MPU 102 in the apparatus 100 to function as a logic analyzer, patient bedside monitor, or other type of equipment.

The flash memory 122 of the location system 118 stores a location application 123, which is executable by the MCU 120. The flash memory 122 also can be used to store one or more security certificates 124 usable for authenticating the apparatus 100 to a remote device receiving packets from the apparatus. A first certificate can be used by the location system's MCU 120 during transmissions with an access point to determine the location of apparatus 100. A second certificate can be used by the MPU 102 when executing application 107 (e.g., to transmit logic analyzer or patient data to a network) and sending/receiving packets to/from a network.

The location system 118 determines, or at least facilitates the determination of, the location of the apparatus 100. In one example, the location system 118 records an identifier of an Wi-Fi access point to which the Wi-Fi transceiver 121 is associated. When prompted for the access point identifier from a remote device, the Wi-Fi transceiver responds with the requested identifier. The physical locations of the access points are known apriori and thus, within the communication range of the access points, the location of the apparatus 100 can be determined. In one implementation, room-level accuracy is possible. In another example, the location system 118 calculates the time of flight of Wi-Fi data frames to any one or more of multiple access points so that the resulting timing information can be used to calculate the location of the equipment containing location system 118. In another example, the sensor 119 connected to MCU 120 can be used to trigger waking the MCU (from a lower power mode of operation) and/or transmission of a notification (e.g., Wi-Fi data frame) to a local access point to send an alert that the equipment has been moved. Once woken, the MCU 120 (or network processor) can receive management requests to, for example, change security parameters such as a digital certificate, an encryption key, etc. In some implementations, an access point can send a data frame to the MCU 120 without having a sensor triggering a wake-up event.

The power circuit 130 includes a power detector circuit 132 and a power switch 134. The power switch 134 may comprise a transistor such as one or more metal oxide semiconductor field effect transistors (MOSFETs). The power detector circuit 132 of the power circuit 130 is coupled to a line voltage source node 150, which itself can be connected to an alternating current (AC) voltage supply such as via a wall outlet or power strip. The power circuit 130 also couples to a battery node 152 of battery 140. When line power is available on voltage source node 150, line power is provided to the embedded system 101 and through power switch 134 to the location system 118. The power detector 132 detects whether the voltage level on the line voltage source node 150 is above a threshold voltage level. The voltage on node 150 being above the threshold indicates that line voltage is available and provided to the apparatus 100. Accordingly, the power detector circuit 132 configures the power switch 134 into the state as shown in FIG. 1 to allow line voltage to be provided through the power switch 134 to the location system 118. If the power detector circuit 132 does not detect a line voltage in excess of the threshold, then the power detector circuit 132 configures the power switch 134 to the opposite state to electrically couple battery 140 to the location system 118. In this latter state, the location system 118 operates from battery power, and the embedded system is non-operational. In another example, battery 140 is rechargeable and is charged when line power is available.

The MCU 120 in this example includes a Wi-Fi transceiver 121. The MCU 120 is electrically coupled to the MPU 102 of the embedded system 101 via communication link 105. The communication link 105 may be serial or parallel and the data frame encapsulation may be chosen for convenient implementation based on the operating system and network stacks used in the apparatus 100. When the apparatus 100 is connected to a source of line power and the embedded system 101 is turned on, the MPU 102 can transmit data to the MCU 120 over link 105, for the MCU 120 to have wirelessly transmitted via its Wi-Fi transceiver 121 to a remote device. Accordingly, the embedded system 101 need not include (but could include) its own Wi-Fi transceiver. If a security certificate is to be used for the transmission of data originated by the MPU 102, a certificate 124 from flash memory 122 can be used. Alternatively, a certificate provided wirelessly to the location system's flash memory 122 can be transmitted via the MCU 120 to the MPU 102 and stored in the embedded system's flash memory 104, and used therefrom for security authentication and other purposes.

In one implementation, the MCU 120 of the location system 118 is fabricated as an integrated circuit (IC) on a semiconductor die, and the MPU 102 of the embedded system 101 is fabricated as an IC on a separate semiconductor die. The flash memory 122 may be fabricated on the same die as the MCU 120, or the flash memory 122 may be fabricated on a separate die from the die containing MCU 120. Similarly, the flash memory 104 and RAM 106 may be fabricated on the same die as the MPU 102, or the flash memory 104 and RAM 106 may be fabricated on a separate die from the die containing the MPU 102. In another implementation, a single semiconductor die can include the MPU 102 and the MCU 120.

FIG. 2 depicts an example of a software architecture implemented on apparatus 100. The software in the embedded system 101 includes an application 107 and a Transmission Control Protocol/Internet Protocol (TCP/IP) stack 204, both of which are stored on flash memory 104 and executed by the MPU 102. The application 202 causes the MPU 102 to provide the functionality of the embedded system (e.g., logic analyzer, bedside monitor, etc.).

The software in the location system 118 includes a location application 210, a TCP/IP stack 212, and a Media Access Control (MAC) data link layer 214, all of which are stored on flash memory 122 and are executed by the MCU 120. The location application 210 causes the MCU 120 to assist in the determination of the location of the apparatus 100. Determining the location of the apparatus also of course means determining the location of any of the components of the apparatus such as the flash memory 122 within the location system 118.

A physical (PHY) layer 216 includes the Wi-Fi transceiver and wirelessly sends and receives packets. Data generated by location application 210 and to be sent as packets to a remote device for location assessment purposes may be encapsulated with headers in accordance with the TCP/IP protocols and provided through the MAC data link layer 214 to the PHY 216 for transmission therefrom. Packets received by the PHY 216 and targeting the location application 210 progress in the opposite direction through, for example, the MAC data link layer 214 and the TCP/IP stack 212.

Data generated by the application 107 of the embedded system 101 is encapsulate with TCP/IP headers by the TCP/IP stack 204 executing on the embedded system's MPU 102. An Application Programming Interface (API) is exposed to the MAC data link layer 214 to permit a packet from the embedded system's TCP/IP stack 204 to be processed by the location system's MAC data link layer 214. As an example, TCP/IP stack 204 sends and receives frames to and from MAC 214 using IEEE 802.3 ethernet format encapsulation.

The hardware architecture of FIG. 1 and the software architecture of FIG. 2 provide several benefits relative to the use of Wi-Fi tags that are not operably connected to the embedded system, and which means the embedded system and the Wi-Fi tag have separate Wi-Fi transceivers. First, the disclosed examples of FIGS. 1 and 2 include a Wi-Fi transceiver 121 that is shared by both the MCU 120 of the location system 118 and the MPU 102 of the embedded system 101. Thus, only one Wi-Fi transceiver need be present (although more than one can be included as desired). Fewer hardware components generally results in a more reliable and less costly system. Second, the software executing on the location system's MCU 120 includes a MAC data link layer 214 that is used by the software executing on the embedded system's MPU 102. Accordingly, the embedded system 101 need not include its own MAC data link layer, thereby simplifying the software design for apparatus 100. Third, because the location system 118 is continuously operational (either line-powered or battery-powered), maintenance operations can be performed wirelessly on the apparatus 100 without locating and physically moving the apparatus to a maintenance area. The location system 118 includes a Wi-Fi transceiver 121 and flash memory 122 which permits, for example, a new security certificate to be wirelessly transmitted to the location system for storage in the flash memory 122 and subsequent use by the embedded system 101 after the embedded system is powered on via line power. Alarms can be triggered through wireless access to the location system 118. For example, if the equipment is determined to be located in an improper location, a wireless message could be sent to the location system 118 to trigger an alarm (e.g., siren, flashing light, voice alert, etc.).

In this description, the term “couple” or “couples” means either an indirect or direct wired or wireless connection. Thus, if a first device couples to a second device, that connection may be through a direct connection or through an indirect connection via other devices and connections. Modifications are possible in the described embodiments, and other embodiments are possible, within the scope of the claims. 

What is claimed is:
 1. A device comprising: a processor; a transceiver; a controller coupled to the processor and the transceiver, wherein the controller is configured to execute a location application, and wherein the processor is configured to send application data to the controller for wireless transmission via the transceiver; and a power management circuit comprising: a first terminal configured to be coupled to a first power source, a second terminal configured to be coupled to a second power source, and a power detector configured to monitor power at the first terminal, wherein the power management circuit is configured to: responsive to detecting power at the first terminal, provide power to the processor and the controller from the first power source, and responsive to not detecting power at the first terminal, provide power to the controller without providing power to the processor.
 2. The device of claim 1, further comprising a sensor coupled to the controller, wherein the sensor is configured to wake the controller upon detection of an event.
 3. The device of claim 2, wherein the sensor comprises a motion sensor or a temperature sensor.
 4. The device of claim 2, wherein the controller is configured to transmit a wireless notification of the even in response to a signal from the sensor.
 5. The device of claim 1, wherein the controller is configured to: receive a wireless wake request; wake up in response to the wireless wake request; and after waking up, receive a management request to change a security parameter.
 6. The device of claim 5, further comprising a memory configured to store the management request.
 7. The device of claim 1, wherein the controller is configured to determine a location of the device based on a data frame.
 8. The device of claim 7, wherein determining the location of the device based on the data frame comprises using a time of flight associated with the data frame.
 9. The device of claim 8, where the data frame is a Wi-Fi data frame.
 10. The device of claim 7, wherein the controller is configured to: generate location data based on the determined location of the device; and transmit the location data using the transceiver.
 11. The device of claim 7, wherein transceiver is configured to communicate with an access point (AP) having an AP location, and wherein the controller is configured to determined the location of the device based on the AP location.
 12. The device of claim 1, wherein the processor is configured to execute a first stack that includes a first transmission control protocol/internet protocol (TCP/IP) layer, wherein the controller is configured to execute a second stack that includes a second TCP/IP layer and a media access control (MAC) layer, and wherein the first and second TCP/IP layers are configured to access the MAC layer using separate application programming interfaces (APIs).
 13. The device of claim 1, wherein the processor is configured to execute a Linux operating system.
 14. The device of claim 1, wherein the first power source is a line power source, and wherein the second power source is a battery power source.
 15. The device of claim 1, wherein the controller is configured to execute the location application to generate location data, the controller further configured to: provide the location data to a first transmission a first transmission control protocol/internet protocol (TCP/IP) stack to generate a location packet based on the location data; and transmit the location packet using the transceiver.
 16. The device of claim 15, wherein the controller is configured to: receive a data packet from a second TCP/IP stack associated with the processor; and in response to receiving the data packet from the second TCP/IP stack, transmit the location packet and the data packet using the transceiver.
 17. The device of claim 16, wherein the controller is further configured provide the location packet and the data packet to a media access control (MAC) layer.
 18. The device of claim 16, further comprising a memory configured to store a security certificate, wherein the data packet is associated with the security transmission, and wherein the controller is configured to, in response to receiving the data packet from the second TCP/IP stack: retrieve the security certificate from the memory; and establish a secure communication link for the data packet based on the security certificate.
 19. The device of claim 18, wherein the memory is configured to store a second security certificate, and wherein the location application is configured to generate the location data using the second security certificate.
 20. The device of claim 1, wherein the processor and the controller are integrated in an integrated circuit. 